Log Received Data to File on the App Server

In addition to the Audit log configurable within App Manager, you can also log a copy of all inbound data to file on the App Server. Messages longer than 2065 bytes will not be truncated within this log as they are in the Audit Log.

 

To enable the log, you need to create the following DWORD Registry Value on the App Server machine:

32-bit Operating Systems:

HKEY_LOCAL_MACHINE\Software\
ndl-metascybe\mx\ConnectMobile\Ver3\Settings\EnableCommsDump

64-bit Operating Systems:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\
ndl-metascybe\mx\ConnectMobile\Ver3\Settings\EnableCommsDump

Set the Value to 1 to enable logging and 0 to disable it again.

When enabled, each request from a Client received by the App Server is written to a separate set of files. Each set consists of two files, one containing the raw data and the other containing the decoded data, with the following file names:

Dump_<sessionID>_<systemtickcount>.raw

Dump_<sessionID>_<systemtickcount>.xml

where:

<sessionID> = a unique log ID identifying the session from which the data comes. You can find out which session an ID refers to by looking through the standard Audit log in App Manager.

<systemtickcount> = time the log was created consisting of the number of milliseconds since the PC was last booted up.

 

The .raw file contains the raw data received and will generally appear as garbage as the data will be encrypted and compressed.

The .xml file contains the decoded data which will allow you to view the contents of messages received and read the data contained within them.

 

By default, the files will be stored in the Digitise Apps logging folder:

C:\ProgramData\NDL Software\Digitise Apps\Logging

 

We recommend that you only enable this logging in the event that you experience a problem for which this logging could be helpful, e.g. where messages are being truncated in the Audit Log and you need to see the whole data or when asked to do so by the NDL Helpdesk. Remember to delete the log files and disable logging once the problem has been rectified as the log files created could potentially be quite large.